System and process for distributed network of redundant central stations

ABSTRACT

Techniques are described for distributing, to a distributed network of central stations, alarm events detected in monitoring system data collected by sensors included in monitoring systems located at monitored properties. A system receives monitoring system data collected by sensors included in monitoring systems located at monitored properties, tracks alarm events detected within the monitoring system data, and generates, for central station servers in a distributed network of central stations, load profiles that reflect a volume of alarm events being handled at each of the central station servers at a particular period of time. The system determines capacities to handle additional alarm events for the central station servers, determines relative priorities for the central station remote servers based on the determined capacities, and directs subsequent alarm events to the central station servers based on the relative priorities.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.15/984,676, filed May 21, 2018, which is a continuation of U.S.application Ser. No. 15/590,147, filed May 9, 2017, now U.S. Pat. No.9,978,240, issued May 22, 2018, which is a continuation of U.S.application Ser. No. 15/069,517, filed on Mar. 14, 2016, now U.S. Pat.No. 9,652,971, issued May 16, 2017, which claims the benefit of U.S.Application Ser. No. 62/132,419, filed on Mar. 12, 2015. All of theseprior applications are incorporated by reference in their entirety.

TECHNICAL FIELD

This disclosure relates to monitoring technology and, for example,creating redundancy by using a distributed network of affiliated centralstations.

BACKGROUND

Central stations receive information from monitoring systems (e.g.,in-home alarm or security systems) and handle dispatching emergencyservices based on critical information sensed by the monitoring systems.Central stations may monitor a large number of user accounts in whichcase system failures may adversely impact performance of individualmonitoring systems and reduce the safety offered by the monitoringsystems. Techniques for directing monitoring data traffic can includeredundantly operating multiple central stations by creating distributednetworks of affiliated central stations to monitor a large number ofuser accounts.

SUMMARY

Techniques are described for improving the operability of monitoring(e.g., alarm or security) systems by creating a distributed network ofaffiliated central stations. Central stations receive information frommonitoring systems (e.g., in-home alarm or security systems) and handledispatching emergency services based on critical information sensed bythe monitoring systems. Central stations may monitor a large number ofuser accounts in which case system failures may adversely impactperformance of individual monitoring systems and reduce the safetyoffered by the monitoring systems. In addition, single central stationsmay be unable to handle large volume of calls related to alarm eventswithout disrupting operation. To help increase reliability of centralstations, techniques are described to redundantly operate multiplecentral stations by creating distributed networks of affiliated centralstations to monitor a large number of user accounts. Central stationstypically work with monitoring systems, but the techniques describedthroughout this disclosure may be applied to any type of monitoringdevice, such as life-support monitoring equipment, emergency medicalmonitoring equipment, standalone fire sensors, standalonecarbon-monoxide sensors, etc.

In some implementations, a system for distributing, to a distributednetwork of central stations, alarm events detected in monitoring systemdata collected by sensors included in monitoring systems located atmonitored properties, includes a server. The server includes at leastone processor and at least one computer-readable storage medium coupledto the at least one processor having stored thereon instructions which,when executed by the at least one processor, causes the at least oneprocessor to perform operations. The operations include receivingmonitoring system data collected by sensors included in monitoringsystems located at monitored properties and tracking alarm eventsdetected within the monitoring system data collected by the sensorsincluded in the monitoring systems located at the monitored properties.The operations further include generating, for central station serversin a distributed network of central stations, load profiles that reflecta volume of alarm events being handled at each of the central stationservers at a particular period of time. The operations includedetermining, based on the generated load profiles and for the centralstation servers in the distributed network of central stations,capacities to handle additional alarm events and determining relativepriorities for the central station remote servers based on thedetermined capacities. The operations conclude with directing subsequentalarm events to the central station servers based on the determinedrelative priorities.

Implementations of the described techniques may include hardware, amethod or process implemented at least partially in hardware, or acomputer-readable storage medium encoded with executable instructionsthat, when executed by a processor, perform operations.

The details of one or more implementations are set forth in theaccompanying drawings and the description below. Other features will beapparent from the description and drawings, and from the claims.

DESCRIPTION OF DRAWINGS

FIGS. 1 and 4 illustrate example systems for creating redundancy using adistributed network of central station servers.

FIGS. 2, 3 7, and 8 are flowcharts illustrating example processes.

FIG. 5 illustrates an example load profile.

FIG. 6 illustrates a process for redirecting data traffic among thedistributed network of central station servers.

DETAILED DESCRIPTION

FIG. 1 illustrates an example of an electronic system 100 configured toredundantly operate multiple central stations using distributed networksof affiliated central stations. The electronic system 100 includes anetwork 105, a monitoring system control unit 110, a distributed stationnetwork 140, and a monitoring application server 150. In some examples,the network 105 facilitates communication between the monitoring systemcontrol unit 110, central station servers 142 and 144, and themonitoring application server 150.

The network 105 is configured to enable exchange of electroniccommunications between devices connected to the network 105. The network105 may include, for example, one or more of the Internet, Wide AreaNetworks (WANs), Local Area Networks (LANs), analog or digital wired andwireless telephone networks (e.g., a public switched telephone network(PSTN), Integrated Services Digital Network (ISDN), a cellular network,and Digital Subscriber Line (DSL)), radio, television, cable, satellite,or any other delivery or tunneling mechanism for carrying data. Thenetwork 105 may include multiple networks or subnetworks, each of whichmay include, for example, a wired or wireless data pathway. The network105 may include a circuit-switched network, a packet-switched datanetwork, or any other network able to carry electronic communications(e.g., data or voice communications). For example, the network 105 mayinclude networks based on the Internet protocol (IP), asynchronoustransfer mode (ATM), the PSTN, packet-switched networks based on IP,X.25, or Frame Relay, or other comparable technologies and may supportvoice using, for example, VoIP, or other comparable protocols used forvoice communications. The network 105 may include one or more networksthat include wireless data channels and wireless voice channels. Thenetwork 105 may be a wireless network, a broadband network, or acombination of networks including a wireless network and a broadbandnetwork.

The monitoring system control unit 110 includes a network module 112 anda controller 114. The controller 114 is configured to control amonitoring system (e.g., a home alarm or security system) that includesthe monitoring system control unit 110. In some examples, the controller114 may include a processor or other control circuitry configured toexecute instructions of a program that controls operation of an alarmsystem. In these examples, the controller 114 may be configured toreceive input from sensors, detectors, or other devices included in thealarm system and control operations of devices included in the alarmsystem or other household devices (e.g., a thermostat, an appliance,lights, etc.). For example, the controller 114 may be configured tocontrol operation of the network module 112 included in the monitoringsystem control unit 110.

The monitoring system control unit 110 may be configured to receiveinput from one or more sensors or detectors 120. For example, themonitoring system control unit 110 may be configured to receive datafrom multiple sensors 120. The sensors 120 may include a contact sensor,a motion sensor, a glass break sensor, or any other type of sensorincluded in an alarm system or a security system. The sensors 120 mayalso include an environmental sensor, such as a temperature sensor, awater sensor, a rain sensor, a wind sensor, a light sensor, a smokedetector, a carbon monoxide detector, an air quality sensor, etc. Thesensors 120 further may include a health monitoring sensor, such as aprescription bottle sensor that monitors taking of prescriptions, ablood pressure sensor, a blood sugar sensor, a bed mat configured tosense presence of liquid (e.g., bodily fluids) on the bed mat, etc. Insome examples, the sensors may include a radio-frequency identification(RFID) sensor that identifies a particular article that includes apre-assigned RFID tag. In addition, the sensors 120 may include avideo/photographic camera or other type of optical sensing deviceconfigured to capture images and may include an energy consumptionsensor for appliances and devices in a property monitored by themonitoring system.

The monitoring system control unit 110 communicates with modules 124 and128 and sensors 120 to perform system monitoring and control. The module124 is connected to one or more appliances, is configured to monitoractivity of the one or more devices, and is configured to controloperation of the one or more appliances. The module 124 may directlymeasure activity of the one or more appliances or may estimate activityof the one or more appliances based on detected usage of the one or moreappliances. The module 124 may communicate energy monitoring informationto the monitoring system control unit 110 and may control the one ormore appliances based on the commands received from the monitoringsystem control unit 110.

The module 128 is connected to a thermostat, is configured to monitortemperature of a temperature regulation system associated with thethermostat, and is configured to control operation of the thermostat.The module 128 may directly measure activity of the temperatureregulation system associated with the thermostat or may estimateactivity of the temperature regulation system associated with thethermostat based on the detected temperature of the temperatureregulation system associated with the thermostat. The module 128 alsomay determine energy usage information based on the activity,communicate energy monitoring information to the monitoring systemcontrol unit 110, and control the thermostat based on commands receivedfrom the monitoring system control unit 110.

The modules 124, 128, and sensors 120 communicate with the control 112over communication links 122, 126, and 130, respectively. Thecommunication links 122, 126, and 130 may be a wired or wireless datapathway configured to transmit signals from the modules 124, 128, andsensors 120 to the controller 112. The modules 124, 128, and sensors 120may continuously transmit sensed values to the controller 112,periodically transmit sensed values to the controller 112, or transmitsensed values to the controller 112 in response to a change in a sensedvalue.

The network module 112 is a communication device configured to exchangecommunications over the network 105. The network module 112 may be awireless communication module configured to exchange wirelesscommunications over the network 105. For example, the network module 112may be a wireless communication device configured to exchangecommunications over a wireless data channel and a wireless voicechannel. In this example, the network module 112 may transmit monitoringdata over a wireless data channel and establish a two-way voicecommunication session over a wireless voice channel. The wirelesscommunication device may include one or more of an LTE module, a GSMmodule, a radio modem, cellular transmission module, or any type ofmodule configured to exchange communications in one of the followingformats: LTE, GSM or GPRS, CDMA, EDGE or EGPRS, EV-DO or EVDO, UMTS, orIP.

The network module 112 also may be a wired communication moduleconfigured to exchange communications over the network 105 using a wiredconnection. For instance, the network module 112 may be a modem, anetwork interface card, or another type of network interface device. Thenetwork module 112 may be an Ethernet network card configured to enablethe monitoring system control unit 110 to communicate over a local areanetwork and/or the Internet. The network module 112 also may be avoiceband modem configured to enable the alarm panel to communicate overthe telephone lines of Plain Old Telephone Systems (POTS).

The distributed station network 140 includes multiple central stations132 and 134 that operate independently and are connected over thenetwork 105. The distributed station network 140 may include many morecentral stations than illustrated in FIG. 1. The multiple centralstation servers 142 and 144 are electronic devices configured to providealarm monitoring services by exchanging communications with themonitoring system control unit 110, and/or the monitoring applicationserver 150 over the network 105. For example, the multiple centralstation servers 142 and 144 may be configured to monitor alarm eventsgenerated by the monitoring system control unit 110. In this example,the multiple central station servers 142 and 144 may exchangecommunications with the network module 114 included in the monitoringsystem control unit 110 to receive information regarding alarm eventsdetected by the monitoring system control until 110. The multiplecentral station servers 142 and 144 also may receive informationregarding alarm events by the monitoring application server 150.

The multiple central stations servers 142 and 144 perform monitoringoperations independently from one another with different monitoringsystem control units over the network 105. For example, the multiplecentral station servers 142 and 144 may monitor monitoring systemcontrol units within different locations and also may be operated bydifferent companies that are not affiliated. In such examples, themultiple central station servers 142 and 144 operate as separateentities within the system 100 and only become affiliated when there isunusually high volumes of monitoring data transmission to one of themultiple central alarm station servers 142 and 144, or there is afailure in one of the central station servers. For instance, the system100 may redistribute the data transmissions from the central stationserver 142 to the central station server 144 if it detects potentialsignal disruptions within the data transmissions to the central stationserver 142.

The monitoring application server 150 is an electronic device configuredto provide monitoring services by exchanging electronic communicationswith the monitoring system control unit 110 and the multiple centralstation servers 142 and 144 over the network 105. For example, themonitoring application server 150 may be configured to monitor events(e.g., alarm events) generated by the monitoring system control unit110. In this example, the monitoring application server 150 may exchangeelectronic communications with the network module 114 included in themonitoring system control unit 110 to receive information regardingevents (e.g., alarm events) detected by the monitoring system controlunit 110.

The monitoring application server 150 also exchanges communications withthe monitoring system control units 110 of multiple monitoring systemswithin different properties over the network 105. For example, thesystem 100 may include multiple monitoring application servers 150 thatmonitor specified monitoring systems based on properties grouped withincertain geographic regions. The monitoring application server 150 maymonitor multiple monitoring systems within a certain locality (e.g., onemile radius) using parallel communication networks to reduce the numberof data transmissions required to monitor all alarm events generated byone or more monitoring system control units 110.

The monitoring application server 150 stores sensor and image datareceived from the monitoring system and performs analysis of sensor andimage data received from the monitoring system. Based on the analysis,the monitoring application server 150 may communicate with and controlaspects of the monitoring system control unit 110. The monitoringapplication server 150 also may store information regarding existingmonitoring data transmissions to the multiple central station servers142 and 144. For example, the monitoring application server 150 maystore a load profile 152 based on the volume of prior monitoring datatransmitted to the multiple central station servers 142 and 144connected over the network 105. The monitoring application server 150also may store a monitoring data repository 154 of minimal data requiredto process monitoring data from the monitoring system control unit 110for properties associated with the multiple central station servers 142and 144.

The load profile 152 and the monitoring data repository 154 may bestored over communication links 156 and 158 in databases 160 and 170,respectively. The communication links 156 and 158 may be a wired orwireless data pathway configured to transmit signals from the monitoringapplication server 150 to databases that store the load profile 152 andthe monitoring data repository 154. The monitoring application server150 may continuously transmit data to the databases, periodicallytransmit data based on alarm events detected by the monitoring controlunit 110, or in response to a data transmission.

In some implementations, the monitoring application server 150 receivesmonitoring data from multiple security service providers that maintainin-home security systems within the properties where the monitoringsystem control units 110 are located. For example, the monitoring datatransmitted may be the minimal data required to process monitoring datafrom the monitoring system control unit 110 for properties associatedwith the multiple central station servers 142 and 144, such as theemergency contact for the property account or the property address. Inthis example, the system 100 may store the monitoring data in themonitoring data repository 154 to track properties that experiencemonitoring events that indicate that the user may require immediateassistance.

In some implementations, the monitoring application server 150 mayindependently gather property information from security serviceproviders and the collective load of the distributed station network 140to intelligently redistribute monitoring data transmission betweenmultiple central stations 142 and 144. For example, the system 100 mayreroute monitoring data from the central alarm station 142 to anothercentral alarm station 144 within the distributed station network 140 ifit determines that the central alarm station 142 is experiencingunusually high volume of monitoring data or is experiencing performanceissues.

FIG. 2 illustrates an example process 200 for transmitting monitoringdata between a distributed network of central stations. The operationsof the example process 200 are described generally as being performed bythe system 100. The operations of the example process 200 may beperformed by one of the components of the system 100 (e.g., themonitoring application server 150) or may be performed by anycombination of the components of the system 100. In someimplementations, operations of the example process 200 may be performedby one or more processors included in one or more electronic devices.

Briefly, the system 100 receives monitoring data from differentconnected security service providers and different connected centralstations (210). The system 100 builds a central repository of necessarydata required to process security events for properties based on thereceived monitoring data (220). The system 100 builds a load profile ofthe connected central stations that reflects volume of monitoring datawithin the connected central stations at each instant in time (230). Thesystem 100 determines a capacity to handle additional monitoring datafor each of the connected central stations based on the load profile(240). The system 100 determines relative priorities of the connectedalarm stations based on comparing the capacities to threshold values(250). Finally, the system 100 transmits the necessary monitoring datafrom the central repository to a central station with a high prioritybased on comparing the capacities to the threshold values (260).

The example process 200 begins when the system 100 receives monitoringdata from different connected security service providers and differentconnected central stations (210). For instance, the system 100 mayreceive monitoring data that identifies attributes of monitoring datagenerated from an alarm event at the property. The attributes ofmonitoring data may include status of the sensors within the property,the monitored status of devices within the property, the emergencycontact for the property account, or the property address. In thisexample, the system 100 may store the monitoring data in an appropriatelocation to track properties that experience alarm events that indicatethat the user may require immediate assistance.

For example, the monitoring data may be stored in the monitoringapplication server 150. In such examples, the monitoring data may bemaintained by third-party security providers that perform service andmaintenance on the property, but not the alarm system. The monitoringapplication server 150 may therefore allow alarm system manufacturers toreceive access to user information that may be necessary to provideemergency assistance service when there is an alarm event within theproperty.

In some implementations, the system 100 may use the monitoring data fromthe monitoring application server 150 to predict the importance of thevarious monitoring data transmitted by the monitoring system controlunit 110. For example, the prediction may include identifying themonitoring data into certain high-priority categories, such as firealarms, carbon dioxide levels, and other monitoring data intolow-priority categories, such as water levels, or brokensensors/equipment. In some implementations, the prediction may involveanalyzing alarm frequency within certain properties over fixed timeperiods (e.g., over a 12 month period) to determine whether highincidence rates indicate a false alarm event. The system 100 may usethis analysis to deprioritize potential monitoring data that may notnecessarily qualify as necessary monitoring data.

The system 100 builds a central repository of necessary data required toprocess security events for properties based on the received monitoringdata (220). For instance, the system 100 may parse the receivedmonitoring data from multiple security service providers and determinethe monitoring data that is essential to process and track the alarmevents that may occur within the properties. In this example, thenecessary data may include the property address and the emergencycontact such that the system 100 may identify and locate the propertyand transmit the necessary monitoring data to a central station foremergency assistance service.

In some examples, the monitoring application server 150 may build amonitoring data repository 154 based on prior monitoring data from themultiple central station servers 142 and 144 and the monitoring data. Insuch examples, the monitoring data repository 154 may represent ahistorical log of prior monitoring data transmitted to the centralstations for properties identified by the information from themonitoring data.

The system 100 builds a load profile of the connected central stationsthat reflects volume of monitoring data within the connected centralstations at each instant in time (230). For instance, the system 100 mayreceive data transmissions from multiple connected central stationservers that indicate prior monitoring data transmissions and ongoingdata processing operations taking place within the central stations. Insuch instances, the system 100 may use the data transmissions to trackthe operations of the connected central station servers and calculatethe load profile 152 based on performance parameters, such as CPU usage,memory usage, CPU usage history, physical memory usage history, andcapacity of operators to handle alarm events and dispatch emergencyservices. The system 100 also may analyze the hardware configurations ofthe central station servers to determine performance thresholds forsubsequent monitoring data transmissions.

In some examples, the monitoring application server 150 stores a loadprofile 152 over a communication link 156 within a database 160. In suchexamples, the monitoring application server continuously monitorsmultiple central station servers 142 and 144 and updates the loadprofile 152 on a reoccurring basis based on the status of the multiplecentral station servers 142 and 144. For example, the monitoringapplication server 150 may determine the current load profile 152 andarchive the prior load profiles in the database 160 in five minuteintervals to determine changes in status of the multiple central stationservers 142 and 144.

The system 100 determines a capacity to handle additional monitoringdata for each of the connected central stations based on the loadprofile (240). For instance, the system 100 may receive datatransmissions from the central stations with performance indicators thatrepresent its usage by other processes related to other alarm events inother properties or locations. The system 100 may use such datatransmissions to calculate how subsequent transmissions of monitoringdata may impact the central station and predict the likelihood ofgenerating a prompt emergency service response to the alarm event withina property.

In some examples, the monitoring application server 150 may determinethe capacity to handle additional monitoring data for multiple centralstation servers 142 and 144 based on the load profile 152 and monitoringdata repository 154 of the multiple central station servers 142 and 144.In such examples, the monitoring application server 150 may determinethe capacity by calculating the resource availability within themultiple central station servers 142 and 144 and a prediction ofexpected monitoring data volume based on the historical log of the priormonitoring data transmitted to the connected central stations within themonitoring data repository 154. The monitoring application server 150may further determine when the multiple central station servers 142 and144 may likely be idle or partly idle based on the load profile 152.

The system 100 determines relative priorities of the connected alarmstations based on comparing the capacities to threshold values (250).For instance, the system 100 may compare the calculated capacity tohandle additional monitoring data to determine whether a particularconnected central station is identified as a high priority center thatmay receive subsequent data retransmissions from a failed centralstation. In such instances, the system 100 may redistribute themonitoring data transmission from the failed central station to a highpriority central station based on its capacity to handle additionalmonitoring data.

For example, the monitoring application server 150 may determine whichof the multiple central station servers 142 and 144 has a higherpriority based on its capacity to handle additional monitoring data todetermine which central station server to send necessary monitoring dataredistributed from a central station server that has been identified asexperiencing service disturbances.

In some implementations, the system 100 may use the relative capacitiesof the connected central station servers to determine the more efficientredundant transmission mechanism to multiple central station servers.For example, the system 100 may determine from the load profiles and thecapacities to handle additional monitoring data that there are certaincentral stations that are licensed to the same territory or location andthat parallel transmission to them may be effective based on theirproximity to one another. In such examples, the system 100 may redirectnecessary monitoring data to these specified central stations tomaximize transmission speed and minimize errors upon transmission.

In some implementations, the system 100 may determine the relativepriorities of the central stations based on subscription services and/oroperating costs. For example, larger, more expensive central stationsmay be used to redistribute monitoring data from properties that agreeto a higher price per signal costs based on their subscription. In suchinstances, the relative priorities of the central stations may bedetermined based on the specific user subscriptions of the monitoringdata that needs to be redistributed. For example, if a property issubscribed to premium alarm system service, then the monitoring datagenerated by the property may only be transmitted to the high prioritycentral station systems, whereas the monitoring data from a propertythat is subscribed to minimal alarm services may be transmitted to lowor medium priority alarm stations.

The system 100 transmits the necessary monitoring data from therepository to a central station with a high priority based on comparingthe capacities to the threshold values (260). For instance, the system100 may redistribute monitoring data from a temporary location withinthe monitoring application server 150 to central servers 142, 144.

In some implementations, the necessary monitoring data may betransmitted to more than one high priority central station based on aload-balance configuration between the connected central stations evenwithout a failed central station. For example, the system 100 maydetermine, based on the capacity to handle additional monitoring datathat redistributing the monitoring data to multiple central stations maybe more advantageous than transmission to the original central station.In such examples, although the original central station may remainfunctional, the system 100 may determine that it is necessary toexpedite the monitoring data based on the severity of the alarm eventwithin the property that generates it. The system 100 may subsequentlytransmit the monitoring data in specific loads to multiple centralstations connected to the same network to increase transmission speedand reduce processing speed by utilizing the processing powers of themultiple central stations.

In some implementations, the system 100 may determine the loaddistribution for the necessary monitoring data to be transmitted basedon real-time utilization reports generated from the central stationsinstead of a load profile 152 of all connected central systems. Forexample, the utilization reports may be transmitted to the applicationmonitoring server, to perform trend analysis on which transmission to acombination of central stations may be most advantageous forredistributing the necessary monitoring data. In such examples, thesystem application monitoring server may consider transmission latenciesbased on the proximities between the connected central stations, thesuccess rate of prior transmissions as indicated on the utilizationreport, and hardware configurations that support parallel dataprocessing procedures to expedite redistributing.

FIG. 3 illustrates an example process 300 for determining the priorityfor a central station to transmit monitoring data. The process 300determines a priority for a connected central station by comparing thecapacity to handle additional monitoring data for the connected centralstations to two thresholds to assign the central station with one of alow, medium, or high priority.

The process 300 begins by comparing the capacity to handle additionalmonitoring data to a low threshold (310). For example, a first, lowthreshold may have a value of 25% and the system 100 may compare adetermined capacity to handle additional monitoring data to the 25%threshold. The system 100 may determine whether the capacity is belowthe low threshold (320). For example, a central station may have beendetermined to have a capacity to handle additional monitoring data at10%, and the system 100 may determine whether the capacity value of 10%is below the threshold of 25%. If the capacity is below the lowthreshold, the central station is handled with a low priority (330),where the process 300 then ends.

If the determined capacity to handle additional monitoring data meetsthe low threshold, the system 100 compares the capacity value comparesthe capacity to a second, high threshold (340). For example, a second,high threshold may have a value of 75% and the system 100 may comparethe determined alarm probability score associated with the alarm eventto the 75% threshold. The system 100 may determine whether the alarmprobability score is below the high threshold (750). For example, acentral station may have been determined to have a capacity of 90%, andthe system 100 may determine whether the capacity value of 90% is belowthe high threshold of 75%. If the alarm probability score is below thehigh threshold, the connected central station is handled with mediumpriority (340), where the process 300 then ends. Alternatively, if thedetermined capacity value is not below the high threshold, the system100 handles the connected central station with high priority (370).After the connected central station has been handled with one of amedium or a high priority, the process 300 ends.

FIG. 4 illustrates an example of an electronic system 400 configured toredundantly leverage multiple central stations using distributednetworks of affiliated central stations. The electronic system 400 canbe an implementation of the electronic system 100, and is shown toinclude many of the same components that function in the same ways as inthe electronic system 100. The electronic system 400 includes a network105, a distributed station network 140, and a monitoring applicationserver 150.

The monitoring application server 150 includes a monitoring data manager402, a load profile generator 404, a capacity manager 406, and apriority manager 408. The monitoring data manager 402 is configured toreceive, transmit, and/or direct monitoring data traffic. The monitoringdata manager 402 receives monitoring data from the network 105. In someexamples, the monitoring data manager 402 gathers monitoring data (e.g.,door open, alarm event, etc.) from a network of properties (e.g., anetwork of monitoring system control units 110 in FIG. 1, although onlyone is depicted in FIG. 1).

The monitoring application server 150 processes the monitoring systemdata from the monitored properties and then alerts a central station inthe event of an alarm that could be in need of emergency services. Thecentral stations receive monitoring data from the monitoring applicationserver 150. While the monitoring application server 150 gets data fromthe central stations, it relates to resolution of alarm eventsdispatched to the central stations and, potentially, data on load.

The monitoring data manager 402 can include a processor or other controlcircuitry configured to execute instructions of a program that processesand controls data traffic. The monitoring data manager 402 can includetransceiver components configured to transmit or receive data fromnetwork 105. In some examples, the monitoring data manager 402communicates directly with the distributed station network 140 and/orits components (e.g., central station servers 142 and 144).

The monitoring data manager 402 can build a central repository ofmonitoring data. In some examples, the monitoring data manager 402creates the monitoring data repository 154 and stores it in database170. The monitoring data manager 402 can receive communications from thepriority manager 408. In some examples, the communications includeinstructions for directing data traffic to the distributed stationnetwork 140.

The monitoring data manager 402 can process received monitoring data toidentify security events (e.g., someone has entered the house, a windowhas been left open, etc.) In some examples, the monitoring data manager402 identifies the security events, flags, or otherwise marks them. Insome implementations, the monitoring data manager 402 identifies thesecurity events and stores the events in a database (e.g., the database170). The monitoring data manager 402 can transmit, to the load profilegenerator 404, the monitoring data or a subset of the monitoring datarelated to alarm events dispatched to the distributed station network140.

The load profile generator 404 is configured to receive and processmonitoring data to generate a load profile for each central stationserver of the distributed station network 140. The load profilegenerator 404 can include a processor or other control circuitryconfigured to execute instructions of a program that generates loadprofiles (e.g., load profiles 152). The load generator 404 can store theload profiles 152 in a database (e.g., database 160). In some examples,the load profile generator 404 generates a graphical representation ofthe load profiles 152.

The load profiles 152 can represent a volume of monitoring data beinghandled by each central station server (e.g., the central stationservers 142 and 144). In some examples, the load profiles 152 aregenerated for a period of time. The period of time can be predetermined,input by a user, or determined by the electronic system 400. The loadprofile generator 404 can transmit the load profiles 154 to the capacitymanager 406.

The capacity manager 406 is configured to determine a capacity to handleadditional monitoring data for each central station server of thedistributed station network 140. The capacity manager 406 uses the loadprofiles 152 generated by the load profile generator 404 to determinethe capacities for each central station server. In some examples,determining a capacity includes calculating a resource availability ineach of the central station servers (e.g., central station servers 142and 144). The capacity manager 406 can generate a prediction of thevolume of expected monitoring data based on historical log data (e.g.,from the monitoring data repository 154). In some examples, themonitoring data manager 402 generates the predictions. The capacitymanager 406 can transmit the capacities for each central station serverto the priority manager 408.

The priority manager 408 is configured to determine a relative priorityfor each central station server of the distributed station network 140.The priorities are relative to each of the other central stationservers, and can indicate the order in which traffic is directed to eachserver. In some examples, determining the relative priorities includescomparing the capacities to thresholds. The thresholds can bepredetermined, input by a user, or determined dynamically by theelectronic system 400. For example, if a flood is triggering alerts inmany security systems in the same area, a lower threshold for capacityto handle additional monitoring data can be lowered to accommodate forthe increase in traffic throughout the distributed station network 140.

In some examples, the priorities for each central station server aredetermined based on server characteristics such as cost, efficiency,reliability, speed, etc. For example, if three central station serversare available with the same base priorities, the priority manager 408can look at other properties of the servers. In this example, one serveris twice as fast as the other two, but is twice as expensive. A secondserver is moderately priced and is the most reliable of the three. Athird server is the least expensive, transmits and processes at the samespeed as the second server, but is not as reliable as the second server.The priority manager 408 can evaluate all server characteristicsprovided and prioritize the servers relative to each other.

The priority manager 408 can update, set, and remove priorities forcentral station servers of the distributed station network 140. Thepriority manager 408 transmits the determined priorities to themonitoring data manager 402. The monitoring data manager 402 uses thepriorities to direct monitoring data traffic to the distributed stationnetwork 140. In some examples, the monitoring data manager 402 directstraffic by communicating instructions through the network 105 to thedistributed station network 140. In some implementations, the monitoringdata manager 402 communicates directly with the central station servers142 and 144 to direct alarm events to the central stations 142 and 144.

In some examples, the electronic system 400 monitors and directs datatraffic for each central station server of the distributed stationnetwork 140. The electronic system 400 also may direct data traffic forfewer than all central station servers of the distributed stationnetwork 140.

FIG. 5 illustrates an example graphical representation of a load profile500 that represents the volume of monitoring data being handled by acentral station server over a period of time. The graphicalrepresentation of the load profile 500 includes a load profile 502, aload axis 504, a temporal axis 506, an upper additional capacitythreshold 508, and a lower additional capacity threshold 510. In someexamples, the graphical representation of the load profile 500 candisplay more than one load profile 502. The load profile 502 can be anexample of the load profile 152.

The load axis 504 can represent the units of load each central stationserver is under. The temporal axis 506 can represent the units of timeat which each point of the load profile 502 is determined, predicted, ormeasured. In some examples, the temporal axis 506 can extend beyond thepresent time to display predicted load included in the load profile 502.In addition, the load profile 502 may display only historical data. Thegraphical representation of the load profile 500 can be transmitted tobe displayed at a client device. In some examples, the graphicalrepresentation of the load profile 500 is not transmitted for display,and is purely for illustrative purposes.

The upper additional capacity threshold 508 and the lower additionalcapacity threshold 510 can include multiple thresholds. The electronicsystem (e.g., the electronic system 400) generating the load profile 502can generate several thresholds to create several priority levels. Forexample, if the load profile 502 is below the upper additional capacitythreshold 508, a corresponding first central station server isexperiencing relatively low load, and can handle a higher amount ofadditional data traffic. If the load profile 502 is between the upperadditional capacity threshold 508 and a mid-upper additional capacitythreshold, a corresponding second central station server is experiencinga moderately low load, and can handle additional data traffic, but lessthan the first central station server. If the load profile 502 is abovethe lower additional capacity threshold 510, a corresponding thirdcentral station server is experiencing relatively high load, and cannothandle additional data traffic.

FIG. 6 illustrates an example process 600 of evaluating the status ofconnected central station servers and redirecting monitoring datatraffic using the electronic system 400. At a time 1, four centralstation servers 602, 604, 606, and 608 are in communication with themonitoring application server 150. The central station servers 602, 604,606, and 608 can communicate with the monitoring application server 150through the network 105. In some examples, the monitoring applicationserver 150 transmits instructions to the network 105. The network 105can transmit the instructions to the central station servers 602, 604,606, and 608 unchanged or processed. Each of the central station servershas a corresponding load profile: load profiles 610, 612, 614, and 616.

The system 400 determines a status of each of the central stationservers 602, 604, 606, and 608. In some examples, the system 400determines a status of the central station servers based on themonitoring data received and the events that have been sent to centralstation servers for processing. For example, the monitoring data can bereceived from security systems installed by security dealers inmonitored properties. The security systems can transmit the monitoringdata to the monitoring application server 150. In some examples, thestatuses are determined by the system 400 based on data in themonitoring application server 150's central repository (e.g., repository154).

In other addition, the central station servers 602, 604, 606, and 608can periodically send status reports directly to the monitoringapplication server 150. The monitoring application server 150 can thendetermine statuses from the received reports. In this case, themonitoring application server 150 may account for capacity being handledby the central station servers that derives from alarm events detectedby security systems that do not use the monitoring application server150.

The system 400 can determine, from the statuses that a server hasexperienced a failure, is busy, or is otherwise operating atypically.Statuses may be determined based on monitoring data. For example, if themonitoring data is an alarm event that is sent to a central stationserver, and the central station server does not response, then thesystem 400 can determine that the status of the central station serveris non-operational. In addition, the system 400 can determine that acentral station server is currently busy and cannot handle anyadditional data traffic. The system 400 can determine from a status thata corresponding central station server has gone offline. The system 400can determine that an adjustment or reevaluation of the alarm data flowis in order.

The load profile 610 of the central station server 602 shows that thecentral station server 602 is operating above a lower additionalcapacity threshold, and is therefore unlikely to process additional datatraffic effectively or quickly. The load profile 612 of the centralstation server 604 shows that the central station server 604 isoperating between a lower and an upper additional capacity threshold,and can process a moderate level of additional data traffic. The loadprofile 614 of the central station server 606 shows that the centralstation server 606 is not processing any data traffic at all, whichsuggests a failure. The load profile 616 of the central station server608 shows that the central station server 608 is operating below anupper additional capacity threshold, and is able to process a high levelof additional data traffic.

In this example, the lack of data traffic shown by the load profile 614indicates that there is abnormal activity surrounding the central server606 and high volume at the central server 602. The abnormal activity canbe related to the communication link between the monitoring applicationserver 150 and the central station server 606, the functioning of thecentral station server 606, etc. For example, the central station server606 can experience a power outage, preventing it from processing anydata directed to it. The high volume at the central server 602 mayintroduce delay or error in processing further alarm events, but alarmevents are being proposed nonetheless.

At a time 2, the central station servers 602, 604, 606, and 608 receivecommunications from the monitoring application server 150. Axis mark 618indicates time 1 and is shown on the graphical representations of eachof the central station servers 602, 604, 606, 608, highlighting thechange in monitoring data traffic between time 1 and time 2.

The system 400 can determine, from the statuses and from comparing thecapacities to handle additional monitoring data priority assignments foreach of the central station servers 602, 604, 606, and 608. The severityof the monitoring data can affect the priorities for each of the centralstation servers. For example, if an alert is received with high severity(e.g., a fire in a high occupancy building) the priorities for eachserver can be adjusted based on the properties of each server. A serverwith high processing bandwidth but low speed can be given a lowerpriority based on the severity of the alert. In some examples, costconsiderations can affect the priority assignments for the centralstation servers 602, 604, 606, and 608. For example, some third-partyservers can offer lower operating or usage prices.

The priority determinations can be made using comparisons of thresholdvalues to each remote server's capacity to handle additional datatraffic as well as the criticality of the data. For example, if anemergency alert is indicated by the monitoring data, the priorityassignments for servers can be altered. Alert factors and historicaldata can be used in determining the priority assignments for the centralstation servers. For example, historical response time to the type orcategory of alert can affect the priority assignment of the centralstation servers. If an alert for a fire and an alert for a burglary areindicated by the monitoring data, priority can be adjusted for theservers to provide the faster response time to the fire alert.

The central station server 602 receives a LOW priority assignment fromthe monitoring application server 150. In some examples, the priorityassignment remains on the monitoring application server 150 and is usedby an electronic system (e.g., electronic system 400) to direct traffic.In some implementations, the priority assignment is received by each ofthe central station servers 602, 604, 606, and 608, which enable thecentral station servers 602, 604, 606, and 608 to monitor capacity,correct issues, and report errors in the priority classifications made.

The graphical representation of the central station server 602illustrates the change in data traffic since time 1. The central stationserver 602 was above the low additional capacity threshold, and wasassigned a LOW priority. The central station server 602 did notexperience an increase in data traffic between time 1 and time 2, due toits LOW priority.

The central station server 604 receives a MEDIUM priority assignmentfrom the monitoring application server 150. The graphical representationof the central station server 604 illustrates the change in data trafficthrough the central station server 604 since time 1. The central stationserver 604 was between the upper additional capacity threshold and thelower additional capacity threshold, and was assigned a MEDIUM priority.The central station server 604 experienced an increase in data trafficafter time 1 while remaining below the lower additional capacitythreshold.

The central station server 606 receives a STOP status from themonitoring application server 150. In some examples, the STOP statusprevents data traffic from being directed to the central station server606. The STOP status may indicate that the central station server 606has ceased processing activity and should not be used. The STOP statusmay be communicated to the central station server 606 to enable thecentral station server 606 to determine that the central station server606 is not being used until it confirms that it is available to processalarm events. The central station server 606 did not receive any furtherdata traffic since time 1.

The central station server 608 receives a HIGH priority assignment fromthe monitoring application server 150. The graphical representation ofthe central station server 608 illustrates the change in data trafficthrough the central station server 608 since time 1. The central stationserver 608 was below the high additional capacity threshold, and wasassigned a HIGH priority. The central station server 608 experienced anincrease in data traffic after time 1, exceeding the upper additionalcapacity threshold, while remaining below the lower additional capacitythreshold.

FIG. 7 illustrates an example process 700 that assigns a priority toexample monitoring data transmitted between a distributed network ofcentral stations. Briefly, the system 100 receives monitoring data fromdifferent security systems (710). The system 100 identifies an alertbased on the received monitoring data (720). The system 100 classifiesthe identified alert into an alert category (730). The system 100determines a severity for the alert category (740). Finally, the system100 assigns a priority to the monitoring data based on the determinedseverity (750).

The operations of the example process 700 are described generally asbeing performed by the system 100. In some examples, the operations ofthe example process 700 can be performed by the system 400 and/or itscomponents (e.g., the monitoring application server 150) or can beperformed by any combination of the components of the system 400. Insome implementations, the operations can be performed by one or moreprocessors included in the one or more electronic devices.

The example process 700 begins when the system 400 receives monitoringdata from different security systems installed by security serviceproviders (710). The system 400 identifies an alert based on thereceived monitoring data (720). For example, the alert can be an alertof a break-in to a home. The alert can be of a fire in a large home withmany people inside. The system 400 classifies the alert into an alertcategory (730). The type of the alert can be determined based on anoccupancy status of property, harm that could result from the alertsituation, etc. For example, the type of an alert can be determinedbased on whether lives are in danger, potential for property damage, orsimply a component malfunction.

The system 400 then determines a severity of the category of alert(740). The severity of a category can be relative to the severities ofthe other categories currently active. In some examples, the severity ofa category is absolute. For example, an alert for a fire in ahigh-occupancy building can be assigned a high severity, no matter whatother alerts are active. An alert for a door left open can be assignedthe highest severity if the other active alerts are alerts, such as acommunication failure with a security component that is historicallyunreliable.

The severity can be determined based on the occupancy, thetime-sensitivity, the response time of available units, whether thealert is preventative, etc. In some examples, the severity is based onthe monitoring data traffic experienced by the distributed stationnetwork 140. For example, if there is a sudden increase in data traffic,the severity of some categories such as no or low-occupancy alerts couldbe reduced or altered.

The system 400 finally assigns a priority to the monitoring dataindicating the alert based on the determined severity (750). In someexamples, the priority is relative to the other monitoring data beingprocessed by the system 400. The priority can be based on the monitoringdata traffic experienced by the distributed station network 140. Thepriority can be based on the specific central station server throughwhich the monitoring data traffic is to be directed. For example, datafor a specific home can be routed through a central station server basedon location. The central station server can suddenly experience anincrease in data traffic, and the priority of the alert for the home canbe altered.

FIG. 8 illustrates an example process 800 for redundantly transmittingexample monitoring data between a distributed network of centralstations. Briefly, the system 100 receives monitoring system datacollected by sensors included in monitoring systems located at monitoredproperties (810). The system 100 tracks alarm events detected within themonitoring system data (820). The system 100 generates load profilesthat reflect a volume of alarm events being handled at each of one ormore central station servers (e.g., distributed station network 140) ata particular period of time (830). The system 100 determines a capacityto handle additional alarm events for each central station server on thedistributed station network 140 based on the generated load profiles(840). The system 100 determines relative priorities for each centralstation server based on the determined capacities (850). Finally, thesystem 100 directs subsequent alarm events to each central stationserver based on the determined relative priorities (860).

The operations of the example process 800 are described generally asbeing performed by the system 100. In some examples, the operations ofthe example process 800 can be performed by the system 400 and/or itscomponents (e.g., the monitoring application server 150) or can beperformed by any combination of the components of the system 400. Insome implementations, the operations can be performed by one or moreprocessors included in the one or more electronic devices.

The example process 800 begins when the system 400 receives capacitydata from different central station servers (810). The system 400 mayreceive monitoring system data collected by sensors included inmonitoring systems located at monitored properties. For example, thesystem 400 receives a video stream, motion sensor data, door sensordata, etc. from John's house. The system 400 then tracks alarm eventsdetected within the monitoring system data (820). For example, thesystem 400 may track an alarm event of Break-In Through Back Doordetected from the door sensor data received.

Next, the system 400 generates, the central station servers in thedistributed network of central stations, load profiles that reflect avolume of alarm events being handled at each of the central stationservers at a particular period of time (830). For example, the system400 may generate a load profile for each central station server forMonday, Feb. 22, 2016. In some examples, the period of time can beselected by a user, predetermined, or calculated by the system 400.

The example process 800 continues when the system 400 determinescapacities to handle additional alarm events for the central stationservers based on the generated load profiles (840). The system 400 thendetermines relative priorities for the central station servers based onthe determined capacities (850). In some examples, the system 400 maydetermine relative priorities for each of the remote servers based oncomparing the determined capacities to at least one threshold value. Thethreshold values can be selected by a user, predetermined, or calculatedby the system 400. In some examples, the threshold values aredynamically calculated, and are based on the amount of data trafficexperienced by the distributed station network 140.

Finally, the system 400 directs subsequent alarm events, transmitted tothe system 400 by monitoring systems and devices located at monitoredproperties, based on the determined relative priorities of each centralstation server (860). In some examples, the priorities are nottransmitted to the central station servers, and are managed by thesystem 400 for directing data traffic.

The described systems, methods, and techniques may be implemented indigital electronic circuitry, computer hardware, firmware, software, orin combinations of these elements. Apparatus implementing thesetechniques can include appropriate input and output devices, a computerprocessor, and a computer program product tangibly embodied in amachine-readable storage device for execution by a programmableprocessor. A process implementing these techniques can be performed by aprogrammable processor executing a program of instructions to performdesired functions by operating on input data and generating appropriateoutput. The techniques can be implemented in one or more computerprograms that are executable on a programmable system including at leastone programmable processor coupled to receive data and instructionsfrom, and to transmit data and instructions to, a data storage system,at least one input device, and at least one output device. Each computerprogram can be implemented in a high-level procedural or object-orientedprogramming language, or in assembly or machine language if desired; andin any case, the language can be a compiled or interpreted language.Suitable processors include, by way of example, both general and specialpurpose microprocessors. Generally, a processor will receiveinstructions and data from a read-only memory and/or a random accessmemory. Storage devices suitable for tangibly embodying computer programinstructions and data include all forms of non-volatile memory,including by way of example semiconductor memory devices, such asErasable Programmable Read-Only Memory (EPROM), Electrically ErasableProgrammable Read-Only Memory (EEPROM), and flash memory devices;magnetic disks such as internal hard disks and removable disks;magneto-optical disks; and Compact Disc Read-Only Memory (CD-ROM). Anyof the foregoing can be supplemented by, or incorporated in, speciallydesigned application-specific integrated circuits (ASICs).

It will be understood that various modifications can be made. Forexample, other useful implementations could be achieved if steps of thedisclosed techniques were performed in a different order and/or ifcomponents in the disclosed systems were combined in a different mannerand/or replaced or supplemented by other components. Accordingly, otherimplementations are within the scope of the disclosure.

What is claimed is:
 1. A system for determining a priority for handlingmonitoring data, the system comprising: a server comprising: at leastone processor; and at least one computer-readable storage medium coupledto the at least one processor having stored thereon instructions which,when executed by the at least one processor, causes the at least oneprocessor to perform operations comprising: receiving monitoring datafrom different security systems installed by security service providersat different monitored properties of different users; identifying analert at a monitored property based on at least a portion of thereceived monitoring data; classifying the alert into an alert category;determining a severity of the alert category into which the alert wasclassified; assigning a priority to the monitoring data indicating thealert based on the determined severity; and handling the monitoring databased on the priority assigned to the monitoring data, whereinclassifying the alert into the alert category comprises: determining anoccupancy status of the monitored property where the alert wasidentified, the occupancy status indicating whether one or more usersare occupying the monitored property at a time of the alert, anddetermining the alert category based on the determined occupancy statusof the monitored property where the alert was identified, and whereinhandling the monitoring data based on the priority assigned to themonitoring data comprises routing, to a central station server andrelative to other monitoring data being processed by the system, themonitoring data based on the priority assigned to the monitoring data,the central station server handling dispatching of emergency services tothe monitored property.
 2. The system of claim 1, wherein classifyingthe alert into the alert category comprises determining the alertcategory based on an amount of harm that could result from situationinvolving the alert.
 3. The system of claim 1, wherein determining theseverity of the alert category into which the alert was classifiedcomprises determining a severity of the alert category relative toseverities of other alert categories that are currently active.
 4. Thesystem of claim 1, wherein determining the severity of the alertcategory into which the alert was classified comprises determining theseverity of the alert category based on an occupancy status of aproperty associated with the alert, a time-sensitivity associated withthe alert, a response time of available units for responding to thealert, or whether the alert is preventative.
 5. The system of claim 1,wherein assigning the priority to the monitoring data indicating thealert based on the determined severity comprises assigning the priorityto the monitoring data relative to other monitoring data being processedby the system.
 6. The system of claim 1, wherein assigning the priorityto the monitoring data indicating the alert based on the determinedseverity comprises assigning the priority to the monitoring data basedon monitored data traffic experienced by a distributed station networkof multiple central station servers.
 7. The system of claim 1, whereinassigning the priority to the monitoring data indicating the alert basedon the determined severity comprises assigning the priority to themonitoring data based on monitored data traffic for a specific centralstation server through which the monitoring data is to be directed.
 8. Asystem for determining a priority for handling monitoring data, thesystem comprising: a server comprising: at least one processor; and atleast one computer-readable storage medium coupled to the at least oneprocessor having stored thereon instructions which, when executed by theat least one processor, causes the at least one processor to performoperations comprising: receiving monitoring data from different securitysystems installed by security service providers at different monitoredproperties of different users; identifying an alert at a monitoredproperty based on at least a portion of the received monitoring data;classifying the alert into an alert category; determining a severity ofthe alert category into which the alert was classified; assigning apriority to the monitoring data indicating the alert based on thedetermined severity; and handling the monitoring data based on thepriority assigned to the monitoring data, wherein determining theseverity of the alert category into which the alert was classifiedcomprises determining the severity of the alert category based onmonitored data traffic experienced by a distributed station network ofmultiple central station servers, and wherein handling the monitoringdata based on the priority assigned to the monitoring data comprisesselecting, from among the multiple central station servers in thedistributed station network, a central station server based on thepriority assigned to the monitoring data and routing the monitoring datato the selected central station server, each of the multiple centralstation servers in the distributed station network being available tohandle dispatching of emergency services to the monitored property. 9.The system of claim 8, wherein determining the severity of the alertcategory based on monitored data traffic experienced by a distributedstation network of multiple central station servers comprises alteringthe severity of the alert category based on an increase in the monitoreddata traffic experienced by the distributed station network of multiplecentral station servers.
 10. A method for determining a priority forhandling monitoring data, the method comprising: receiving monitoringdata from different security systems installed by security serviceproviders at different monitored properties of different users;identifying an alert at a monitored property based on at least a portionof the received monitoring data; classifying the alert into an alertcategory; determining a severity of the alert category into which thealert was classified; assigning a priority to the monitoring dataindicating the alert based on the determined severity; and handling themonitoring data based on the priority assigned to the monitoring data,wherein classifying the alert into the alert category comprises:determining an occupancy status of the monitored property where thealert was identified, the occupancy status indicating whether one ormore users are occupying the monitored property at a time of the alert,and determining the alert category based on the determined occupancystatus of the monitored property where the alert was identified, andwherein handling the monitoring data based on the priority assigned tothe monitoring data comprises routing, to a central station server andrelative to other monitoring data being processed, the monitoring databased on the priority assigned to the monitoring data, the centralstation server handling dispatching of emergency services to themonitored property.
 11. The method of claim 10, wherein classifying thealert into the alert category comprises determining the alert categorybased on an amount of harm that could result from situation involvingthe alert.
 12. The method of claim 10, wherein determining the severityof the alert category into which the alert was classified comprisesdetermining a severity of the alert category relative to severities ofother alert categories that are currently active.
 13. The method ofclaim 10, wherein determining the severity of the alert category intowhich the alert was classified comprises determining the severity of thealert category based on an occupancy status of a property associatedwith the alert, a time-sensitivity associated with the alert, a responsetime of available units for responding to the alert, or whether thealert is preventative.
 14. The method of claim 10, wherein assigning thepriority to the monitoring data indicating the alert based on thedetermined severity comprises assigning the priority to the monitoringdata relative to other monitoring data being processed by the system.15. The method of claim 10, wherein assigning the priority to themonitoring data indicating the alert based on the determined severitycomprises assigning the priority to the monitoring data based onmonitored data traffic experienced by a distributed station network ofmultiple central station servers.
 16. The method of claim 10, whereinassigning the priority to the monitoring data indicating the alert basedon the determined severity comprises assigning the priority to themonitoring data based on monitored data traffic for a specific centralstation server through which the monitoring data is to be directed. 17.A method for determining a priority for handling monitoring data, themethod comprising: receiving monitoring data from different securitysystems installed by security service providers at different monitoredproperties of different users; identifying an alert at a monitoredproperty based on at least a portion of the received monitoring data;classifying the alert into an alert category; determining a severity ofthe alert category into which the alert was classified; assigning apriority to the monitoring data indicating the alert based on thedetermined severity; and handling the monitoring data based on thepriority assigned to the monitoring data, wherein determining theseverity of the alert category into which the alert was classifiedcomprises determining the severity of the alert category based onmonitored data traffic experienced by a distributed station network ofmultiple central station servers, and wherein handling the monitoringdata based on the priority assigned to the monitoring data comprisesselecting, from among the multiple central station servers in thedistributed station network, a central station server based on thepriority assigned to the monitoring data and routing the monitoring datato the selected central station server, each of the multiple centralstation servers in the distributed station network being available tohandle dispatching of emergency services to the monitored property. 18.The method of claim 17, wherein determining the severity of the alertcategory based on monitored data traffic experienced by a distributedstation network of multiple central station servers comprises alteringthe severity of the alert category based on an increase in the monitoreddata traffic experienced by the distributed station network of multiplecentral station servers.